Hi All
Every time I run Visio 2007 software, the wizard installation opens.
When I click on "cancel" the wizard window closed and then the Visio software opens.
I am using with win7 64bit.
Any information would be appreciated
thank in advance
Technology Tips and News
Hi All
Every time I run Visio 2007 software, the wizard installation opens.
When I click on "cancel" the wizard window closed and then the Visio software opens.
I am using with win7 64bit.
Any information would be appreciated
thank in advance
Hi,
Try the following steps:
Create a new domain account, add to domain admins, log on using this account, launch VISIO. Rename the profile, then log back. Copy all data from old profile and done.
Similar case here to reference:
I too had the same problem on one of our machines - what I found is that I had to go though a number of different registry keys in HKEY_CLASSES_ROOT and modify all of them so they no longer pointed to the visio viewer. Once I had removed all instances pointing to viewer I found that it was then working again. Here is a list of my keys and their settings that got rid of the issue:
.vsd - (default) Visio.Drawing.11
Content Type application/vnd.visio
.vsl - (default) Visio.AddOn.11
Content Type application/vnd.visio
.vss - (default) Visio.Stencil.11
Content Type application/vnd.visio
.vst - (default) Visio.Template.11
Content Type application/vnd.visio
.vsu - (default) Visio.CustomUI.11
Content Type application/vnd.visio
.vsw - (default) Visio.Workspace.11
Content Type application/vnd.visio
.vsx - (default) Visio.Stencil.11
Content Type application/vnd.visio
.vtx - (default) Visio.Template.11
Content Type application/vnd.visio
I Hope this helps resolve the issue if like me the originally posted fix doesn't resolve the issue. Please remember that editing the registry is not to be done without understanding the risks involved & that if you're not careful you can cause irreversible damage to your system. As such I accept to no Liability for the information contained with this post.
I too had the same problem on one of our machines - what I found is that I had to go though a number of different registry keys in HKEY_CLASSES_ROOT and modify all of them so they no longer pointed to the visio viewer. Once I had removed all instances pointing to viewer I found that it was then working again. Here is a list of my keys and their settings that got rid of the issue:
.vsd - (default) Visio.Drawing.11
Content Type application/vnd.visio
.vsl - (default) Visio.AddOn.11
Content Type application/vnd.visio
.vss - (default) Visio.Stencil.11
Content Type application/vnd.visio
.vst - (default) Visio.Template.11
Content Type application/vnd.visio
.vsu - (default) Visio.CustomUI.11
Content Type application/vnd.visio
.vsw - (default) Visio.Workspace.11
Content Type application/vnd.visio
.vsx - (default) Visio.Stencil.11
Content Type application/vnd.visio
.vtx - (default) Visio.Template.11
Content Type application/vnd.visio
I Hope this helps resolve the issue if like me the originally posted fix doesn't resolve the issue. Please remember that editing the registry is not to be done without understanding the risks involved & that if you're not careful you can cause irreversible damage to your system. As such I accept to no Liability for the information contained with this post.
I too had the same problem on one of our machines - what I found is that I had to go though a number of different registry keys in HKEY_CLASSES_ROOT and modify all of them so they no longer pointed to the visio viewer. Once I had removed all instances pointing to viewer I found that it was then working again. Here is a list of my keys and their settings that got rid of the issue:
.vsd - (default) Visio.Drawing.11
Content Type application/vnd.visio
.vsl - (default) Visio.AddOn.11
Content Type application/vnd.visio
.vss - (default) Visio.Stencil.11
Content Type application/vnd.visio
.vst - (default) Visio.Template.11
Content Type application/vnd.visio
.vsu - (default) Visio.CustomUI.11
Content Type application/vnd.visio
.vsw - (default) Visio.Workspace.11
Content Type application/vnd.visio
.vsx - (default) Visio.Stencil.11
Content Type application/vnd.visio
.vtx - (default) Visio.Template.11
Content Type application/vnd.visio
I Hope this helps resolve the issue if like me the originally posted fix doesn't resolve the issue. Please remember that editing the registry is not to be done without understanding the risks involved & that if you're not careful you can cause irreversible damage to your system. As such I accept to no Liability for the information contained with this post.
I too had the same problem on one of our machines - what I found is that I had to go though a number of different registry keys in HKEY_CLASSES_ROOT and modify all of them so they no longer pointed to the visio viewer. Once I had removed all instances pointing to viewer I found that it was then working again. Here is a list of my keys and their settings that got rid of the issue:
.vsd - (default) Visio.Drawing.11
Content Type application/vnd.visio
.vsl - (default) Visio.AddOn.11
Content Type application/vnd.visio
.vss - (default) Visio.Stencil.11
Content Type application/vnd.visio
.vst - (default) Visio.Template.11
Content Type application/vnd.visio
.vsu - (default) Visio.CustomUI.11
Content Type application/vnd.visio
.vsw - (default) Visio.Workspace.11
Content Type application/vnd.visio
.vsx - (default) Visio.Stencil.11
Content Type application/vnd.visio
.vtx - (default) Visio.Template.11
Content Type application/vnd.visio
I Hope this helps resolve the issue if like me the originally posted fix doesn't resolve the issue. Please remember that editing the registry is not to be done without understanding the risks involved & that if you're not careful you can cause irreversible damage to your system. As such I accept to no Liability for the information contained with this post.
I have been beating my head against the wall for about a year with a VISIO 2007 start-up problem. VISIO ran fine when 1st installed, but at some point broke, triggering the Windows Configuration Installer, to run every time I opened VISIO 2007, from a .vsd drawing file or the VISIO.EXE. I also had prior installed Office 2010 Professional on the same Windows 7 SP1 machine. I tried all mentioned registry hacks and file associations mentioned in this and other threads, but nothing helped.
However the Windows Update titled "2007 Office System Update" KB2767916 dated February 12, 2013 was installed on my machine. I uninstalled this KB2767916 update and the problem is now [SOLVED]. The Windows Configuration Installer no longer tries to run and VISIO opens lightning quick, no matter if executing a .vsd .vst or the VISIO.EXE, including the desktop shortcut. see the article below for a detailed description of this update. DO NOT INSTALL.
https://support2.microsoft.com/kb/2767916?wa=wsignin1.0
TonyI have been beating my head against the wall for about a year with a VISIO 2007 start-up problem. VISIO ran fine when 1st installed, but at some point broke, triggering the Windows Configuration Installer, to run every time I opened VISIO 2007, from a .vsd drawing file or the VISIO.EXE. I also had prior installed Office 2010 Professional on the same Windows 7 SP1 machine. I tried all mentioned registry hacks and file associations mentioned in this and other threads, but nothing helped.
However the Windows Update titled "2007 Office System Update" KB2767916 dated February 12, 2013 was installed on my machine. I uninstalled this KB2767916 update and the problem is now [SOLVED]. The Windows Configuration Installer no longer tries to run and VISIO opens lightning quick, no matter if executing a .vsd .vst or the VISIO.EXE, including the desktop shortcut. see the article below for a detailed description of this update. DO NOT INSTALL.
https://support2.microsoft.com/kb/2767916?wa=wsignin1.0
TonyI have been beating my head against the wall for about a year with a VISIO 2007 start-up problem. VISIO ran fine when 1st installed, but at some point broke, triggering the Windows Configuration Installer, to run every time I opened VISIO 2007, from a .vsd drawing file or the VISIO.EXE. I also had prior installed Office 2010 Professional on the same Windows 7 SP1 machine. I tried all mentioned registry hacks and file associations mentioned in this and other threads, but nothing helped.
However the Windows Update titled "2007 Office System Update" KB2767916 dated February 12, 2013 was installed on my machine. I uninstalled this KB2767916 update and the problem is now [SOLVED]. The Windows Configuration Installer no longer tries to run and VISIO opens lightning quick, no matter if executing a .vsd .vst or the VISIO.EXE, including the desktop shortcut. see the article below for a detailed description of this update. DO NOT INSTALL.
https://support2.microsoft.com/kb/2767916?wa=wsignin1.0
TonyThis fixed the problem for me. Thank you stuart_b!I too had the same problem on one of our machines - what I found is that I had to go though a number of different registry keys in HKEY_CLASSES_ROOT and modify all of them so they no longer pointed to the visio viewer. Once I had removed all instances pointing to viewer I found that it was then working again. Here is a list of my keys and their settings that got rid of the issue:
.vsd - (default) Visio.Drawing.11
Content Type application/vnd.visio
.vsl - (default) Visio.AddOn.11
Content Type application/vnd.visio
.vss - (default) Visio.Stencil.11
Content Type application/vnd.visio
.vst - (default) Visio.Template.11
Content Type application/vnd.visio
.vsu - (default) Visio.CustomUI.11
Content Type application/vnd.visio
.vsw - (default) Visio.Workspace.11
Content Type application/vnd.visio
.vsx - (default) Visio.Stencil.11
Content Type application/vnd.visio
.vtx - (default) Visio.Template.11
Content Type application/vnd.visio
I Hope this helps resolve the issue if like me the originally posted fix doesn't resolve the issue. Please remember that editing the registry is not to be done without understanding the risks involved & that if you're not careful you can cause irreversible damage to your system. As such I accept to no Liability for the information contained with this post.
"However the Windows Update titled "2007 Office System Update" KB2767916 dated February 12, 2013 was installed on my machine. I uninstalled this KB2767916 update and the problem is now [SOLVED]."
This is what fixed the problem for me under Win7 32bit.